Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Why do file sizes change between Windows to Mac drive?

I'm moving a large number of files from a 3TB Windows NTFS external drive to a 3TB Mac OS Extended Journaled external drive.


Now, comparing the original file to the copy, I'm finding that the file sizes in the Get-Info window are different on many of the files. (I would say the majority of them.)


Did something go wrong and do I now have corrupted data across thousands of files? Or does a NTFS drive calculate size differently as a Mac-formatted drive, even though the files are identical?

Posted on Oct 29, 2013 10:39 AM

Reply
7 replies

Oct 29, 2013 12:10 PM in response to Plenty7

Does it happen on all kind of files, or just txt files?


Usually, it comes from the fact that Unix (from which OS X closely derives) and Windows don't have the same way of "recording" changing lines in txt files: in DOS and Windows, going to the next line, whether manually when typing or because you imported a txt file made by someone else (or another machine) means using a "carriage return" (yeah, I know, sounds old), where Unix uses a "line feed".


A carriage return will first send the carret back to the beginning of the last line you typed in, before switching to the next line so you can resume typing, whereas a line feed will jump to the next line directly. This leads to some invisible extra characters being typed, and since each digit or key press brings its own byte or octet in the balance, your files might end up being heavier under one platform than they were in another.


The Notepad application in Windows is known for its poor text wrapping (which it makes up for by being a good tool for coding, for the same reason), with the user/writer needing to feed its own carriage returns in the text, when Wordpad is more user-friendly, with better text wrapping, but doesn't show the same flexibility that Notepad has.


The same principle applies to all txt-based files, hence to .log files too. And log files tend to be created by applications for this purpose or that, without you knowing it.

Oct 29, 2013 12:36 PM in response to Plenty7

As Kappy stated (and I believe Apple started doing that with Snow Leopard), a GB is not reported as its correct size, but the dummied down rounded off number. It's the same thing hard drive makers have been doing for quite a few years now. They report a drive as having a capacity of 500 GB based on the wrong definition of the number of bytes in a GB. So the drive is really about 485 GB.


This dumb, and quite honestly, dishonest way of showing drive sizes has even caused the industry to now have two definitions for the same thing:


GB, which used to be the only and correct term, now means the incorrect size


GiB now means the actual size


Also, the Mac OS has a twin file system for each file and folder on the drive. The data fork, and the resource fork. Each added resource fork (which doesn't exist on any MS formatted drive) adds a few Kbytes to each total file size.

Oct 29, 2013 2:02 PM in response to FrenchToast

(Original poster)


I'm running a Toast "compare" right now (about halfway done) going through each and every file of 3TB on both drives. So far, I'm seeing mismatches on "icon" files (or is it "lcon" with a lower case L?) and I'm seeing mismatches on ".toast" DVD disc images and ".sd2f" disc images.


The disc images (DVD and CD) are the most prone to mismatching in the HDD comparisons. Not a single problem with any other files so far, other than those "lcon" files, whatever they are.

Oct 29, 2013 4:44 PM in response to Plenty7

(Original poster)


My "compare" program has been running for several hours, comparing both drives - the NTFS and the Mac OS Extended (Journaled), looking for mismatches.


There have been a few files here and there, PDFs and what-not, but when I click on the original and the duplicate, they both open properly, even though the file size reads differently for each.


By far the most frequent size difference is in disc images ... ".toast" files (for DVDs) and ".sd2f" files (for CDs). (Both encoded by Toast.)


Only those file types show up very frequently as file size mismatches, which causes me to suspect they're not corrupted and instead being read differently on the two different drives.


Any guess why disc images would consistently be read differently and most other files be read as identical in size?

Why do file sizes change between Windows to Mac drive?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.